Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

✨ backport to release-2.4: use goreleaser for releasing binary #4945

Merged

Conversation

nrb
Copy link
Contributor

@nrb nrb commented Apr 22, 2024

Manually backporting #4748 due to conflicts in hack/tools/go.{mod,sum}.

NONE

* use goreleaser for releasing the binaries

Signed-off-by: Anurag <[email protected]>

* disable releasing of binaries using make targets

since we intend to use goreleaser now, we can remove the make targets.
This commit does the same.

Signed-off-by: Anurag <[email protected]>

* Update release-binaries target to use goreleaser

* Add goreleaser as a tool dependency
* Update .goreleaser configuration to upload YAML templates as GitHub
  release artifacts
* Create binaries rather than archives to mimic current uploads.

Signed-off-by: Nolan Brubaker <[email protected]>

* Update documentation and remove unused targets

Signed-off-by: Nolan Brubaker <[email protected]>

* Remove unused gh targets/client

Signed-off-by: Nolan Brubaker <[email protected]>

* Updates based on doing dry runs

* Remove Windows format override
* Move goreleaser invocation into the Makefile
* Add output directory to goreleaser configuration
* Use generated release notes as the release contents
* Run make release target inside the GitHub workflow
* Set expected environment variables in the GitHub workflow
* Build goreleaser before running the release target

Signed-off-by: Nolan Brubaker <[email protected]>

* Updates based on doing dry runs

* Remove Windows format override
* Move goreleaser invocation into the Makefile
* Add output directory to goreleaser configuration
* Use generated release notes as the release contents
* Run make release target inside the GitHub workflow
* Set expected environment variables in the GitHub workflow
* Build goreleaser before running the release target
* Force goreleaser to use local config
* Set RELEASE_TAG env variable for release notes
* Output env vars for debugging
* Re-enable changelog support

Signed-off-by: Nolan Brubaker <[email protected]>

* Remove reference to unused steps

Signed-off-by: Nolan Brubaker <[email protected]>

---------

Signed-off-by: Anurag <[email protected]>
Signed-off-by: Nolan Brubaker <[email protected]>
Co-authored-by: Nolan Brubaker <[email protected]>
@k8s-ci-robot k8s-ci-robot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-priority size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Apr 22, 2024
@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Apr 22, 2024
@nrb nrb changed the title ✨ use goreleaser for releasing binary (#4748) ✨ backport: use goreleaser for releasing binary (#4748) Apr 22, 2024
@nrb nrb changed the title ✨ backport: use goreleaser for releasing binary (#4748) ✨ backport to release-2.4: use goreleaser for releasing binary (#4748) Apr 22, 2024
@nrb nrb changed the title ✨ backport to release-2.4: use goreleaser for releasing binary (#4748) ✨ backport to release-2.4: use goreleaser for releasing binary Apr 22, 2024
@nrb
Copy link
Contributor Author

nrb commented Apr 22, 2024

/area release

@k8s-ci-robot k8s-ci-robot added the area/release Issues or PRs related to releasing label Apr 22, 2024
Copy link
Member

@damdo damdo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the backport.
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 23, 2024
@damdo
Copy link
Member

damdo commented Apr 23, 2024

/assign @richardcase

@richardcase
Copy link
Member

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: richardcase

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 23, 2024
@damdo
Copy link
Member

damdo commented Apr 23, 2024

/ok-to-test

@k8s-ci-robot k8s-ci-robot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Apr 23, 2024
@k8s-ci-robot k8s-ci-robot merged commit ceabdfb into kubernetes-sigs:release-2.4 Apr 23, 2024
30 of 34 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/release Issues or PRs related to releasing cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants